Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure the broker service name doesn't change #168

Merged
merged 1 commit into from
Nov 21, 2024
Merged

Ensure the broker service name doesn't change #168

merged 1 commit into from
Nov 21, 2024

Conversation

hardillb
Copy link
Contributor

Description

Revert the change of service name so exising Node-RED instances can reconnect to the New EQMX broker after an upgrade.

Related Issue(s)

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

  • Includes a DB migration? -> add the area:migration label

@hardillb
Ensure the broker service name doesn't change
150810b 
This prevents failures on upgrade
@hardillb hardillb requested a review from ppawlowski November 21, 2024 11:29
@hardillb hardillb self-assigned this Nov 21, 2024
@ppawlowski ppawlowski merged commit 04a36fc into main Nov 21, 2024
2 checks passed
@ppawlowski ppawlowski deleted the fix-broker-service-name branch November 21, 2024 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ppawlowski ppawlowski ppawlowski approved these changes

Assignees

@hardillb hardillb

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@hardillb @ppawlowski